Domain UPDATE Request

Function

This request is used to update the data of a domain.

Requirements

The request can only be processed if the domain exists and is administered by the RegAcc that submits the request.

Features

  • You cannot use an UPDATE request to change the domain holder. To change the holder, use the CHHOLDER request.
  • If you omit optional keywords, any values entered for these keywords will be deleted and they will be set to their defaults.
  • If new name servers are specified for a UPDATE request and the predelegation check fails for this, the request is rejected with an "error" and the owner data is not changed.

  • The order of the name servers can change as a result of a domain UPDATE request. The name server order is always output in the same way in the query with the domain INFO request. A new update can change the order again.

Verification

  • A domain UPDATE request automatically triggers a risk assessment.

  • A domain UPDATE is still possible if contacts without a phone number or email are used.

  • When the request is forwarded to the risk assessment, a notification is generated when the new protocol status changes to “pendingCreate” (transition “failed” → “pendingCreate”).

Request Parameters

A Domain UPDATE request is composed of the fields of the "Domain" data object and some other parameters, which are described below:

K/V Keyword XML Namespace and Element Occurrence
min - max		 Type / Length Value Range Description
Action domain:update 1 enumeration update-erule This is the request type.
Version - 1 enumeration version-erule This is the version. The keyword is only relevant for requests in the key/value format.
CtId ctid 0 - 1 token
3 - 64		 Any visible Unicode character (according to Unicode version 3.1) This is the unique transaction ID which is issued by the client.

Common Mistakes

  • The domain stated in the request does not exist.
  • One of the Contacts stated in the request does not meet the requirements of the role to be assigned to it.
  • The Holder stated in the request is not identical with the current holder of the domain.

 

Examples

Copy

request:domainUPDATE
format:kv

Version: 5.0
Action: UPDATE
Domain: domain-example-nsentry.de
Holder: DENIC-1000022-EXAMPLE-PERSON
Generalrequest: DENIC-1000022-EXAMPLE-GR
Abusecontact: DENIC-1000022-EXAMPLE-ABUSE
Nsentry: domain-example-nsentry.de IN A 127.0.0.1
Copy

response:domain
UPDATEformat:kv

RESULT: success
INFO: 53000080014 Domain "Status" is "pendingCreate"
STID: afdd1680-6d5e-4e94-a77a-8ef4a267c6b1

 

Copy

request:domainUPDATE
format:xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<registry-request xmlns="http://registry.denic.de/global/5.0" xmlns:domain="http://registry.denic.de/domain/5.0" xmlns:dnsentry="http://registry.denic.de/dnsentry/5.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <domain:update>
    <domain:handle>domain-example-nsentry.de</domain:handle>
    <domain:contact role="holder">DENIC-1000022-EXAMPLE-XML-PERSON</domain:contact>
    <domain:contact role="abusecontact">DENIC-1000022-EXAMPLE-XML-GR</domain:contact>
    <domain:contact role="generalrequest">DENIC-1000022-EXAMPLE-XML-ABUSE</domain:contact>
    <dnsentry:dnsentry xsi:type="dnsentry:A">
      <dnsentry:owner>domain-example-nsentry.de</dnsentry:owner>
      <dnsentry:rdata>
        <dnsentry:address>81.91.170.12</dnsentry:address>
      </dnsentry:rdata>
    </dnsentry:dnsentry>
  </domain:update>
  <ctid>xml-74ba5156</ctid>
</registry-request>
Copy

response:domainUPDATE
format:xml

<?xml version="1.0" encoding="UTF-8"?>

<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
  <tr:transaction>
    <tr:stid>a503e644-635c-4253-b598-84d0c2296a97</tr:stid>
    <tr:result>success</tr:result>
    <tr:ctid>xml-74ba5155</tr:ctid>
    <tr:result>success</tr:result>
    <tr:message level="info" code="53000080014">
      <tr:text>Domain "Status" is "pendingCreate"</tr:text>
    </tr:message>
  </tr:transaction>
</registry-response>